Remove this paragraph, as the driver handles this on its own. When you iterate the cursor beyond a batch, the driver will issue a getMore to pull in the next batch for continued iteration. When the cursor ID comes back as zero, the driver knows not to issue further getMore commands and prohibits further iteration beyond whatever remains in the last batch.

I see - this applies only for the shell method I guess? Misunderstood a comment you made in the previous review.

The behavior in PHPLIB's Database::command() (and PHPC's executeCommand()) method is probably unique. Other drivers may have a separate method for the envelope handling (see: runCursorCommand in the driver spec).

AFAIK, db.runCommand() returns the raw response with no envelope unpacking, and I don't think the shell has a command cursor variant. I'm also not aware of any way in the shell to construct a cursor object from a raw response, so a script written for mongosh would probably need to manually execute getMore commands.

But more generally, if you have a cursor object in the driver or shell, you can trust that it will use getMore as needed to continue iteration. And db.runCommand() does not give you a cursor.